coverage: 95.367% (+14.2%) from 81.176%
when pulling c255666 on 7ttp:fix-rpcfails
into af85057 on supabase:master.

Thanks for the PR @7ttp ! This is a good fix for the cross-schema type inference issue. A few things to address:

• The error message mentions wrong API. The CrossSchemaError type says:

  Use .rpc<YourReturnType>() to specify the return type explicitly.

But rpc doesn't accept a return type parameter. The JSDoc example correctly shows .overrideTypes<>(). Please update the error message to match:

  type CrossSchemaError<TableRef extends string> = {
    error: true
  } & `Function returns SETOF from a different schema ('${TableRef}'). Use 
  .overrideTypes<YourReturnType>() to specify the return type explicitly.`

• Can you please add a type test to prevent regressions? There's an existing pattern in packages/core/postgrest-js/test/override-types.test-d.ts. Something like:

  // Test cross-schema rpc falls back to Returns type
  {
    const result = await postgrest
      .schema('other_schema')
      .rpc('cross_schema_fn', {})

    expectType<{ id: string; user_id: string }[]>(result.data)
  }

Otherwise the approach looks good. Falling back to Returns type when the table isn't in the current schema is the right solution, and fixing the Relationships lookup to handle missing views is a nice catch.

Updated everything as requested,
Please rereview when available!